Fix application service not being able to join remote federated room without a profile set#13131
Conversation
| "Failed to get profile information while processing remote join for %r: %s", | ||
| target, | ||
| e, | ||
| ) |
There was a problem hiding this comment.
Same pattern that we already use in
synapse/synapse/handlers/message.py
Lines 640 to 652 in e714b8a
| profile = self.profile_handler | ||
| if not content_specified: | ||
| content["displayname"] = await profile.get_displayname(target) | ||
| content["avatar_url"] = await profile.get_avatar_url(target) |
There was a problem hiding this comment.
Feels like these profile functions would be better if they just returned None when there is no profile for the local user. Profiles aren't required.
synapse/synapse/handlers/profile.py
Lines 104 to 129 in e714b8a
synapse/synapse/handlers/profile.py
Lines 201 to 225 in e714b8a
There was a problem hiding this comment.
Yeah, I agree. Pretty much everywhere uses the same pattern as here, and we already return None if the user sets and then deletes their display name
erikjohnston
left a comment
There was a problem hiding this comment.
Happy for this to land as is, or to refactor calls to the profile store
|
Will merge for now ⏩ Thanks for the review @erikjohnston 🐹 |
#399) Synapse changes: matrix-org/synapse#13131 to address matrix-org/synapse#4778
Fix application service not being able to join remote federated room without a profile set
Fix #4778
Complement tests: matrix-org/complement#399
Pull Request Checklist
EventStoretoEventWorkerStore.".code blocks.Pull request includes a sign off(run the linters)